Whenever I try to load any IWAD it gives me a Segmentation Violation. However these IWADS run fine in other engines like PrBoom. Here's an example. I run this command:

vavoom -doom1 -iwaddir ~/wads/doom1/doom1.wad -debug -debug_decorat

In Vavoom, it could be anything <!-- s:-) --><img src="{SMILIES_PATH}/icon_smile.gif" alt=":-)" title="Smile" /><!-- s:-) -->. There are no helpful error messages. Maybe we could determine something if you provided more information. What's the name of th

[quote="b0rsuk":38m8va5f]In Vavoom, it could be anything <!-- s:-) --><img src="{SMILIES_PATH}/icon_smile.gif" alt=":-)" title="Smile" /><!-- s:-) -->. There are no helpful error messages. Isn't the following message helpful? [q

Okay, sorry for that.

This crash is odd, seems you are trying to load a shareware IWAD file, right? Do you know which version of IWAD it is?

It's shareware 1.9. I tried it with Freedoom and Blasphemer and they fail with the same error message. All of these IWADs run in other engines fine though.

I just got GCC 4.5.2 through my update manager. I tried compiling Vavoom 1.33 with it, but Vavoom still gives me the same error messages.

I'll try to load a shareware IWAD ASAP.

Well, they work fine for me, both the Freedoom and Doom shareware wads work without crashing. So I don't know what else could trigger the crashes for you.

Actually I think it might not be loading what I put in -iwaddir. For some reason, no matter what I use for -iwaddir, it starts out with this:

Adding /usr/local/share/vavoom/basev/common/basepak.pk3
adding /usr/local/share/vavoom/doom2&#

[quote="BondEar":33y1sxnz] NOTE: doom2.wad is a symlink to freedoom.wad. That's all it loads. Do you have any idea what's going on with this? Why won't it load what's in -iwaddir? I know the answer. Sor

Tilde expansion is a [u:eygmxalg]shell[/u:eygmxalg] feature, that has nothing to do with "relative paths".

I'm closing this as not a bug then <!-- s:) --><img src="{SMILIES_PATH}/icon_smile.gif" alt=":)" title="Smile" /><!-- s:) -->.

[quote="b0rsuk":1mtlx2i3]Vavoom doesn't understand relative paths on Linux. You're launching with ~/something, where "~" is basically the same as $HOME, right ? In my case, my username is b0rsukThe freedoom.wad file you included isn't for Doom1 it's for Doom2, to run it, you need to use '-doom2' parameter in the command line

$ vavoom -doom2
Adding /usr/local/share/vavoom/base

[quote="BondEar":2xx0aobn][quote="Firebrand":2xx0aobn]The freedoom.wad file you included isn't for Doom1 it's for Doom2, to run it, you need to use '-doom2' parameter in the command line

$ vavoom -doom2